docs: Remove V2 code examples from V3 documentation - #6271
Merged
lucasjia-aws merged 1 commit intoSep 14, 2026
Merged
lucasjia-aws merged 1 commit into
lucasjia-aws merged 1 commit into
Conversation
The V3 documentation site showed side-by-side V2/V3 code blocks on the Training, Inference, MLOps, and Lineage Tracking pages. The V2 blocks are complete, runnable examples using removed APIs (Estimator, Model, Predictor, sagemaker.workflow, SKLearnProcessor, sagemaker.lineage), so readers and crawlers could copy code that does not run on V3. Remove the V2 blocks and keep only the V3 examples: - training/index.rst: drop the Estimator/estimator.fit() quick start - inference/index.rst: drop the Model/Predictor/predictor.predict() block - ml_ops/index.rst: drop the "Traditional Pipeline Approach" block - ml_ops/lineage.rst: drop all 9 "V2 (Legacy)" blocks in Use Cases 1-9 On the Lineage page the V2 and V3 blocks were identical apart from the import path, so no information is lost. Where a lead-in sentence framed a V2-to-V3 comparison, it is rewritten to describe the V3 example directly. The V2-to-V3 API mapping tables are intentionally left in place; they are tracked separately for a possible move into migration.md.
jam-jee
approved these changes
Sep 14, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The V3 documentation site showed side-by-side V2/V3 code blocks on the Training, Inference, MLOps, and Lineage Tracking pages. The V2 blocks are complete, runnable examples using removed APIs (Estimator, Model, Predictor, sagemaker.workflow, SKLearnProcessor, sagemaker.lineage), so readers and crawlers could copy code that does not run on V3.
Remove the V2 blocks and keep only the V3 examples:
On the Lineage page the V2 and V3 blocks were identical apart from the import path, so no information is lost. Where a lead-in sentence framed a V2-to-V3 comparison, it is rewritten to describe the V3 example directly.
The V2-to-V3 API mapping tables are intentionally left in place; they are tracked separately for a possible move into migration.md.
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.